home *** CD-ROM | disk | FTP | other *** search
- Path: news.corp.sgi.com!news!scotth
- From: scotth@sgi.com (Scott Henry)
- Newsgroups: comp.sys.sgi.hardware,comp.lang.c++
- Subject: Re: Help with serial/tty2 communication (write ok, read NOT).
- Date: 12 Feb 1996 18:09:12 GMT
- Organization: Silicon Graphics Inc, Mountain View, CA
- Message-ID: <SCOTTH.96Feb12100912@skuld.corp.sgi.com>
- References: <4ebkuaINNdqp@retriever.cs.umbc.edu> <4ef62p$8t2@ni1.ni.net>
- <TROYS.96Feb12160640@donald.wormald.com.au>
- Reply-To: scotth@sgi.com
- NNTP-Posting-Host: skuld.corp.sgi.com
- In-reply-to: troys@donald.wormald.com.au's message of Mon, 12 Feb 1996 06:06:39 GMT
-
-
- In article <TROYS.96Feb12160640@donald.wormald.com.au> troys@donald.wormald.com.au (Troy Stephen) writes:
-
- > I have a similar problem, and thought it might as well continue on this thread.
-
- > Also, I am a bit concerned about the reliability of the serial ports at
- > high baud rates, especially when the man page for SERIAL(7) says:
-
- > "...Each line may be independently set to run at any of several speeds,
- > as high as 19,200 or even 38,400 bps."
-
- > What are people's experience with this? I need to run at 38.4kbaud and
- > my application needs to read the 27 byte packets at 60hz. What are my
- > chances of getting this to work reliably?
-
- Methinks the man page needs to be updated... 38400 works perfectly
- fine on R3k Indigos and more recent machines. You *may* need to
- worry about flow control (I don't know how big the serial buffer
- is), but people get away with modem cables missing RTS on 1500 byte
- PPP/SLIP packets at 38400, so you are probably OK.
-
- --
- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
- Scott Henry <scotth@sgi.com> / Help! My disclaimer is missing!
- Networking Services, / GIGO *really* means: Garbage in, Gospel Out
- Silicon Graphics, Inc /
- <a href="http://reality.sgi.com/employees/scotth/">home page</a>
-